FIXES TO DCC/2 1.11, DC FOR DAE 1.11 and 7524 Interface Support 1.02
--------------------------------------------------------------------
This file catalogs fixes made to DCC/2 1.11 since we shipped on 6-28-96.
DC for DAE 1.11 was shipped at the same time. 7524 Interface Support 1.02
was originally shipped on 2-23-96.
This file also explains how to install the fixes from the DCC111FX.EXE
self-extracting zip file.
See the bottom of the file for the date of the last change.
If you have the file DCC111FX.EXE you can either create a diskette from
which to install the fixes or you can expand the self-extracting zip file
on the hard drive in any subdirectory and run the installation from that
subdirectory.
IMPORTANT NOTE 1:
These fixes can only be installed if your PC has been rebooted since you
installed DCC/2 or DC for DAE 1.11. The installation makes use of some
environment variables that are defined by CONFIG.SYS.
IMPORTANT NOTE 2:
Since this fix package also contains fixes to 7524 Interface Support you must
apply the fixes after 7524 Interface Support is installed (if you are using
that product). Therefore in the situation where you had already installed
DCC/2 1.11 and had applied the fix package and later you installed 7524
Interface Support, you will need to reapply the fix package so that both
DCC/2 and 7524 Interface Support are at the same level.
EXPANDING AND INSTALLING FROM THE HARD DRIVE
--------------------------------------------
To expand and install DCC111FX.EXE from somewhere on your hard drive,
perform the following steps:
1) Create or choose an empty directory anywhere on your harddrive. For
example: C:\TEMP
2) Copy or download DCC111FX.EXE to that directory
3) Make sure that directory is the current directory and then run the
executable by typing:
DCC111FX
This will expand all the files into the current directory.
4) To install the fixes, first make sure none of the components of DCC/2
(or DC for DAE) are running and that the current directory is the one
containing the expanded contents of the DCC111FX executable. Issue the
following command:
INSTALL
5) Continue with the section below marked: CHRONOLOGICAL SUMMARY OF
FIXES/CHANGES
EXPANDING AND INSTALLING FROM A DISKETTE
----------------------------------------
To create a diskette from the DCC111FX.EXE self-extracting executable,
perform the following steps:
1) Get a completely blank, formatted 1.44 3.5 in. diskette
2) Make sure the DCC111FX.EXE is somewhere on your hard drive, for example
C:\TEMP\DCC111FX.EXE. But DO NOT copy this file to the diskette. If
you do, there will not be enough room to expand all the files contained
in the self-extracting executable.
3) Make A: the current drive
4) If your executable is in C:\TEMP\DCC111FX.EXE then run the following
command:
C:\TEMP\DCC111FX
This will extract the files from the executable and put them on the
diskette because A: is the current drive.
5) To install the fixes contained on the fix diskette, first make sure none
of the components of DCC/2 1.11 are running and then put the fix diskette
in drive A: Issue the following command:
A:\INSTALL
CHRONOLOGICAL SUMMARY OF FIXES/CHANGES
--------------------------------------
6-2-96: Redid tracing so that 7524 IS runs with the new LINETRAC facility
that is part of DCC/2 1.11.
Changed file: \DCC2R\BIN\DCXRFOS2.EXE
7-17-96: Fixed bug in monitor which caused a trap whenever a status command
was issued to the monitored terminal.
Changed file: \DCC2R\BIN\DCXMON.EXE
7-14-96: Added detection of new parameter in EXTRA.CFG: DISABLE_DUP_TX_MSGS.
If found, it causes DCC/2 1.11 to not display messages DCX-090, DCX-144 and
DCX-262.
Changed file: \DCC2R\BIN\DCXCPOS2.EXE
8-2-96: Fixed problem in migration of validation files. A flag in the header
was being set to indicate that the records in the file were sorted when in
fact they are not. The flag is now always set to indicate the records are
in random order.
Changed file: \DCC2R\BIN\VAL.EXE
8-14-96: For both 7524 IS and the TCP/IP support of the 32-bit runtime, we
changed what happens for a transaction release failure. We no longer send
an A1X out right away. Instead we set a flag which will cause the A1X to be
sent only if the terminal is inactive for a while (SLOW_POLL_RATE). This
gets terminals out of a loop where they would send duplicates, DCC/2 would
try to release the duplicates and that would fail causing more duplicates to
be sent from the terminal.
Changed files: \DCC2R\BIN\DCXRFOS2.EXE
\DCC2R\BIN\DCXIPOS2.EXE
8-28-96: Fixed timing problem with the ARTIC interface code. The problem
was more prevalent on faster machines and could manifest itself in
several ways: commands to terminals could be lost; terminals could be
dropped from the polling loop and still show up as In Service and Polled;
communications to all terminals could freeze - requiring DCC/2 to have to
be shut down and restarted. At the same time you would receive a slew of
duplicate transactions from the same terminal.
Changed file: \DCC2R\BIN\DCXIAPI.EXE
8-28-96: Migration of job files now continues with other clusters/jobs if
a .CFG file is not found for one of the clusters. In the past, the migration
would stop with the failing cluster/job.
Changed file: \DCC2R\BIN\JOB.CMD
9-9-96: Fixed the problem where selected terminals were not preserved on the
Terminals page of the Operate notebook when leaving and coming back to the
page.
Changed file: \DCC2R\BIN\OPERATE.EXE
----------------------------------------------------------------------------
End of fixes in 1.01 version of fix package (9-9-96).
----------------------------------------------------------------------------
10-10-96: Fixed the problem where an IP address of the maximum length was
having the last digit lopped off by the Setup notebook.
Changed file: \DCC2R\BIN\SETUP.EXE
10-11-96: We no longer allow the reset or forced reset load options for a
7524 terminal. There was very little use for this ability but there was the
potential to get the terminal in a loop where it could not be downloaded
without shutting down and restarting DCC/2.
Changed files: \DCC2R\BIN\OPERATE.EXE
\DCC2R\BIN\DCXCPOS2.EXE
11-12-96: Fixed two bugs in the TCP/IP code which resulted in more
communications errors than there should have been. One bug resulted
in too quick timeouts and the other resulted in DCC/2 thinking a message
came from an invalid IP address. Also increased the retry count for
each command to 3 from 2.
Changed file: \DCC2R\BIN\DCXIPOS2.EXE
11-19-96: Fixed year 2000 problem in the 32-bit runtime that slipped by our
first check. Note: other parts of DCC/2 may have year 2000 problems.
Changed file: \DCC2R\BIN\DCXCPOS2.EXE
----------------------------------------------------------------------------
End of fixes in 1.02 version of fix package (12-16-96).
----------------------------------------------------------------------------
1-17-97: Fixed a couple of problems on the Exports page of the Setup notebook.
If you added several exports at the same time in which the first 6
characters were the same, the generated logfile name would be the same for
all of them. The logfile names are supposed to be unique. Also had
problem when reading in an export that had no groups assigned. You are
allowed to save the file that way and you just get a warning. However, when
reading in the file with an export of that nature, you'd get a pop-up
stating there was an incomplete definition and the export was removed
from the configuration. This kind of export is now read in properly.
Changed file: \DCC2R\BIN\SETUP.EXE
1-31-97: Fixed problem for 7527 terminal where the transaction buffer was
not properly allocated if it exceeded 99999 bytes. We were trying to
squeeze 6 bytes into 5.
This changes fixes APAR PQ00922.
Changed file: \DCC2R\BIN\DCXCPOS2.EXE
2-02-97: Redid building of validation file list when a .JOB file is created
during migration. All terminal-resident files are now first in the list.
This changes fixes APAR PQ00926.
Changed file: \DCC2R\BIN\JOB.CMD
2-11-97: Changed code to get a terminal out of the not-responding state if a
transaction or download request comes from the terminal when in this state.
This shouldn't be necessary if the port timeout is sufficient. Mechanisms
are already in place for DCC/2 to reestablish communications with a terminal
that has been powered on or comes back into range after being out of range
of the nearest base.
However, we have seen cases where it takes more than a minute for a terminal
to respond to an Are-you-there poll and there was no indication that the
terminal went out of range or was powered off and on. In this situation,
DCC/2 put the terminal in the not-responding state. Later when a
transaction came in, the terminal would be told not to send any more.
With the new change, the terminal may still be told this initially - but
right after that DCC/2 will go through its initialization steps with the
terminal which should cause the terminal to be put back into the in-service
state - provided the terminal responds properly to these steps.
This change is needed mostly for the RF environment - however, since there
is a lot of common code for RF and TCP/IP networks, the change has also
works in the TCP/IP environment.
Changed files: \DCC2R\BIN\DCXRFOS2.EXE
\DCC2R\BIN\DCXIPOS2.EXE
2-27-97: LINETRAC will now keep looping trying to get the shared memory of the
port task it is to trace. In addition, it no longer requires that DCC/2
be running when you start it. This allows tracing of the commands sent
to terminals during startup.
The format of the time stamp in a trace was also changed from 'mmmmmmmmm'
(milliseconds) to 'ssssssss.mmm' (seconds.milliseconds).
Finally, instead of having the FILTER_POLLS parameter we now have a parameter
called SHOW_POLLS (although FILTER_POLLS will still be accepted) for use
when tracing COMx lines. If neither parameter is specified, the default is
now to filter out polls.
Changed files: \DCC2R\BIN\DCXRFOS2.EXE
\DCC2R\BIN\DCXIPOS2.EXE
\DCC2R\BIN\D2XNPO.EXE
\DCC2R\BIN\LINETRAC.EXE
2-27-97: Fixed two problems in the TCP/IP port driver. The response timeout
was not very accurate; rounding errors could raise it by 1 or 2 seconds.
As a result, the startup might time out if you had lots of terminals
configured but not attached. The timing should also be slightly more
accurate for the RF port driver.
A startup synching problem with the gateway task was also fixed. This
problem was not apparent unless you had > 32 TCP/IP terminals configured.
You'd get no terminals on line 0 responding until after startup.
Changed files: \DCC2R\BIN\DCXRFOS2.EXE
\DCC2R\BIN\DCXIPOS2.EXE
3-25-97: Terminals assigned to ARTIC cards other than ARTIC 0 were not being
saved with the proper ARTIC card assignment; they'd always end up on ARTIC 0.
Changed file: \DCC2R\BIN\SETUP.EXE
4-07-97: Increased the time we wait for the port task and gateway tasks to
start up. We found that 5 seconds was not always enough for the TCP/IP
task - especially on busy systems. We now wait 20 seconds. Also added
a more specific message that is logged if this timeout is exceeded.
Changed file: \DCC2R\BIN\DCXIAPI.EXE
4-07-97: Fixed problem that prevented transactions from being collected in
the TCP/IP network. The 2/27 change had a bug in it.
Changed file: \DCC2R\BIN\DCXIPOS2.EXE
----------------------------------------------------------------------------
End of fixes in 1.03 version of fix package (04-15-97).
----------------------------------------------------------------------------